Device, system and method for real-time personalization of streaming video

ABSTRACT

A device, system and method for real-time personalization of streaming video is provided. The device has access to a memory storing: nonpersonalized video segments; and data for rendering personalized video segments, the nonpersonalized video segments and the personalized video segments associated with a given order. When a request for a personalized video is received, the device causes rendering of at least a subset of the personalized video segments to be rendered using the data, incorporating personal data associated with the request into the personalized video segments. As the personalized video segments are rendered, the device updates and transmits a manifest, to the communication device, identifying available video segments according to the given order. The video segments identified in the manifest are provided to the communication device in response to receiving requests for the video segments.

FIELD

The specification relates generally to streaming video, and specificallyto a device, system and method for real-time personalization ofstreaming video.

BACKGROUND

Personalization of video is a growing field. For example, an entity,such as a company, may use a client database, and the like, topersonalize a video on a client-by-client basis, for example byincorporating text of a name of a particular client from the databaseinto at least some portions of a video, as the entire video is beingrendered. The entire video, personalized for the particular client maythen be stored in a memory and/or a database, and a link to the entirevideo may be transmitted to a device of the client (e.g. via an email,and the like) so that the entire video, which is personalized for thespecific client, may be requested via the link. However, when the videois to be personalized for a plurality of names of clients, and the like,for example as part of a marketing campaign, videos are generallyproduced personalized for each of the plurality of names, and at leaston a one-to-one basis for the plurality of names; links to each of therespective personalized videos are transmitted to each of respectivedevices of the clients. When the number of names of clients is in thethousands, tens of thousands, hundreds of thousands, and the like, thenumber of videos produced becomes commensurately very large, which usesa large amount of processing resources. Furthermore, a large amount ofmemory is allocated to store the videos, which may need to be stored fora lengthy period in the event, for example, a client doesn't request thevideo for days, months and/or years and/or in the event a clientrequests the video more than once; hence, memory for storing thousands,tens of thousands, hundreds of thousands, and the like, of personalizedvideos may need to be allocated for a lengthy period, whether thepersonalized videos are requested or not. Indeed, in some instances,more than one video in different formats may be produced for each of theplurality of names, for example with different resolutions, differentframe rates, different video types (e.g. MPEG2TS vs MP4 file types,and/or other file types) and the like, which again increases use ofprocessing and memory resources.

BRIEF DESCRIPTIONS OF THE DRAWINGS

For a better understanding of the various embodiments described hereinand to show more clearly how they may be carried into effect, referencewill now be made, by way of example only, to the accompanying drawingsin which:

FIG. 1 depicts a system for real-time personalization of streamingvideo, in accordance with some embodiments.

FIG. 2 depicts a device diagram showing a device structure of anelectronic computing device for real-time personalization of streamingvideo, in accordance with some embodiments.

FIG. 3 depicts a flowchart of a method for real-time personalization ofstreaming video, in accordance with some embodiments.

FIG. 4 depicts example data for rendering a personalized segment of astreaming video, in accordance with some embodiments.

FIG. 5 depicts an example of rendering a personalized layer of apersonalized segment of a streaming video, in accordance with someembodiments.

FIG. 6 depicts an example of rendering a personalized segment of astreaming video using the personalized layer of FIG. 5, in accordancewith some embodiments.

FIG. 7 depicts an example of producing a personalized icon, inaccordance with some embodiments.

FIG. 8 depicts an example of initiating rendering of a personalizedvideo via a webform, in accordance with some embodiments.

FIG. 9 depicts generating an example initial manifest when initiatingrendering of a personalized video via a webform, in accordance with someembodiments.

FIG. 10 depicts updating an example manifest and providing a firstprerendered video segment of a personalized video, in accordance withsome embodiments.

FIG. 11 depicts providing a first personalized video segment of apersonalized video, in accordance with some embodiments.

FIG. 12 depicts again updating an example manifest and completingrendering of a personalized video, in accordance with some embodiments.

FIG. 13 depicts an example of initiating rendering of a personalizedvideo via a message, in accordance with some embodiments.

DETAILED DESCRIPTION

An aspect of the specification provides a device comprising: acommunication interface; and a controller having access to a memorystoring: nonpersonalized video segments; and data for renderingpersonalized video segments, the nonpersonalized video segments and thepersonalized video segments associated with a given order, thecontroller configured to: receive, from a communication device, usingthe communication interface, a request for a personalized video; causerendering of at least a subset of the personalized video segments usingthe data for rendering the personalized video segments and incorporatingpersonal data associated with the request; generate, and transmit to thecommunication device, using the communication interface, a manifestidentifying at least a first video segment selected according to thegiven order; update, and transmit to the communication device, using thecommunication interface, the manifest to identify, according to thegiven order, further available video segments, as rendering of each ofthe personalized video segments is completed; and provide to thecommunication device, using the communication interface, as thepersonalized video, video segments identified in the manifest, inresponse to receiving requests for the video segments from thecommunication device.

Another aspect of the specification provides a method comprising:receiving, at a device, from a communication device, using acommunication interface, a request for a personalized video, the devicehaving access to a memory storing: nonpersonalized video segments; anddata for rendering personalized video segments, the nonpersonalizedvideo segments and the personalized video segments associated with agiven order; causing rendering of at least a subset of the personalizedvideo segments using the data for rendering the personalized videosegments and incorporating personal data associated with the request;generating, and transmitting to the communication device, using thecommunication interface, a manifest identifying at least a first videosegment selected according to the given order; updating, andtransmitting to the communication device, using the communicationinterface, the manifest to identify, according to the given order,further available video segments, as rendering of each of thepersonalized video segments is completed; and providing to thecommunication device, using the communication interface, as thepersonalized video, video segments identified in the manifest, inresponse to receiving requests for the video segments from thecommunication device.

Attention is directed to FIG. 1 which depicts a system 100 for real-timepersonalization of streaming video. System 100 comprises a computingdevice 101 in communication with a memory 103, such as a databasedevice, and the like. While the memory 103 is depicted as separate fromthe computing device 101, the memory 103 may be a component of thecomputing device 101 and/or another device of the system 100.

The computing device 101 is further in communication with a number “M”of a plurality of video processing devices 105-1 . . . 105-M,interchangeably referred to hereafter, collectively, as the videoprocessing devices 105 and, generically, as a video processing device105. While the video processing devices 105 are depicted as separatefrom the computing device 101, one or more of the video processingdevices 105 may be components of the computing device 101 and/or anotherdevice of the system 100. For example, the computing device 101 may beconfigured to at least temporarily dedicate a portion of processingresources to implement the one or more of the video processing devices105. Alternatively, one or more of the video processing devices 105and/or the computing device 101 may implement functionality of the videoprocessing devices 105 via one or more of an anonymous function, afunction literal, lambda abstraction, lambda expression and/or a lambdafunction, and the like.

Furthermore, the number of “M” video processing devices 105 may besimilar to a number of personalized video segments to be rendered for apersonalized video, as described in more detail below, however thenumber of “M” video processing devices 105 may be less than or greaterthan a number of personalized video segments to be rendered for apersonalized video. Either way, when the number of “M” video processingdevices 105 is two or more, the number of “M” video processing devices105 may be configured to render personalized video segments in parallel.

As depicted, the computing device 101 is in further communication with aplurality of communication devices 107-1 . . . 107-N, interchangeablyreferred to hereafter, collectively, as the communication devices 107and, generically, as a communication device 107, each of which aregenerally configured for requesting and playing streaming video, asdescribed in more detail below. While the computing device 101 isdepicted as being in communication with all the communication devices107, the computing device 101 may be in communication with thecommunication devices 107 at different points in time, for example aseach of the communication devices 107 request personalized videos for arespective user associated with each of the communication devices 107.The number “N” of communication devices 107 may be as few as onecommunication device 107 or may be as many as tens, hundreds, thousands,hundreds of thousands, or more communication devices 107. The computingdevice 101 and the communication devices 107 may be in communication viarespective communication connections and/or paths, and the like,represented by arrows in FIG. 1, which may include one or more wiredand/or wireless communication networks, including, but not limited to,one or more of: a cellular communication network, a Bluetooth™communication network, an NFC (near field communication) communicationnetwork, a WLAN (wireless local area network), a WiFi communicationnetwork (e.g. one or more local area communication network, a WiMax(Worldwide Interoperability for Microwave Access, operating inaccordance with an IEEE 902.16 standard) communication network, a packetbased communication network, the Internet, an analog communicationnetwork, the PSTN (public switched telephone network) and the like.Furthermore, each of the communication devices 107 may comprise one ormore of a cell-phone, a smartphone, a personal computing device, alaptop computing device, a tablet computing device and/or any othercommunication device configured to communicate over a communicationnetwork to request video from the computing device 101.

The computing device 101 may comprise of a plurality of computingdevices and/or servers, for example in a cloud computing arrangementand/or a cloud computing environment; any of such plurality of computingdevices and/or servers may be executing functionality of the computingdevice 101 in a distributed fashion, sequentially or in parallel, acrossthe one or more computing devices. Such cloud computing devices and/orservers may include, but are not limited to, the video processingdevices 105. Any of such plurality of computing devices and/or serversmay be geographically co-located or remotely located and inter-connectedvia electronic and/or optical connections and/or paths, and the like.The computing device 101 may comprise one or more web servers configuredto respond to requests for content from the communication device 107,including, but not limited to, requests for a personalized video.

In general, the memory 103 stores: nonpersonalized video segments 111-1,111-2, 111-3, 111-4, 111-5 (each labelled “NP VS”, where “NP VS”represents the term “Non-Personalized Video Segment”); and data 112-1,112-2, 112-3, 112-4 (each labelled “Data PVS”, where “PVS” representsthe term “Personalized Video Segment”), the data 112-1, 112-2, 112-3,112-4 for rendering personalized video segments, as described in moredetail below. The nonpersonalized video segments 111-1, 111-2, 111-3,111-4, 111-5, will be interchangeably referred to hereafter,collectively, as the nonpersonalized video segments 111, and,generically, as a nonpersonalized video segment 111; similarly, the data112-1, 112-2, 112-3, 112-4, will be interchangeably referred tohereafter, collectively, as the data 112 and/or, and, generically, as aset of data 112. Furthermore the nonpersonalized video segments 111 andthe data 112 may be identified using a Universally Unique Identifier(UUID) a Globally Unique Identifier (GUID) and the like, which may beused to identify a specific set of nonpersonalized video segments 111and data 112. Similarly, each of the nonpersonalized video segment 111and each set of data 112 may be identified using respective UUIDs, GUIDsand the like.

As depicted, the memory 103 further stores icon data 113 for rendering apersonalized icon, as described in more detail below with respect toFIG. 7. The icon data 113 may specifically associated with the set ofnonpersonalized video segments 111 and data 112 and/or may be generic,with a UUID, GUID, and the like, accordingly identifying the icon data113.

The nonpersonalized video segments 111 and the personalized videosegments to be rendered from the data 112 are generally associated witha given order; for example, as depicted, the nonpersonalized videosegments 111 and the personalized video segments to be rendered from thedata 112 are associated with a given order shown by the order of thenonpersonalized video segments 111 and the data 112. In other words, asdepicted, the nonpersonalized video segment 111-1 is first in the givenorder, a personalized video segment to be rendered from the data 112-1is second in the given order, etc. It is understood, however, that inFIG. 1 the personalized video segments to be rendered from the data 112has not yet been rendered.

Together, however, the given order of the nonpersonalized video segments111 and the personalized video segments to be rendered from the data 112represent a personalized video that may be rendered and provided (e.g.streamed) to a communication device 107, for example by the computingdevice 101 upon request from a communication device 107.

While the memory 103 is depicted as storing only one set ofnonpersonalized video segments 111 and data 112 for renderingpersonalized video segments, the memory 103 may further store aplurality of sets of associated nonpersonalized video segments and datafor rendering personalized video segments to render differentpersonalized videos. For example, a first set of associatednonpersonalized video segments and data for rendering personalized videosegments may be used to render a personalized video for a holidaygreeting, while a second set of associated nonpersonalized videosegments and data for rendering personalized video segments may be usedto render a personalized video for a sales campaign and/or a marketingcampaign.

The computing device 101 may be configured to provide content to thecommunication devices 107 requesting such content therefrom, including,but not limited to a personalized video streamed to each communicationdevice 107. However, the personalized video, as a whole, is generallynot rendered prior to receiving a request for the personalized video.

Rather, nonpersonalized video segments 111 are generally prerendered,while personalized video segments are rendered from the data 112 uponreceiving a request for the personalized video, for example usingpersonal data associated with the request. Furthermore, a portion of thedata 112 may include one or more prerendered layers that are notpersonalized and data for rendering a personalized layer of thepersonalized video. Once the nonpersonalized video segments 111 and thepersonalized video segments, rendered from the data 112, are provided toa communication device, the personalized video segments may be deletedand/or discarded such that only the nonpersonalized video segments 111and the data 112 are stored long-term; in other words, personalizedvideos are provided “on-demand” and not prerendered. However in someembodiments, the video rendered from the nonpersonalized video segments111 the personalized video segments are rendered from the data 112 maybe stored at least temporarily and/or a given time period in the eventthe video is again requested such that rendering a second time isobviated.

As described in more detail below, the data 112 includes data used torender a personalized layer using personal data, that may be combinedwith one or more of prerendered static layers and prerendered non-staticlayers; the data 112 may also comprise such prerendered static layersand/or prerendered non-static layers.

Such personal data used to render a personalized layer may be stored ina database 115, for example as personal data 116-1 . . . 116-N,interchangeably referred to hereafter, collectively, as the personaldata 116 and, generically, as a set of personal data 116. The number “N”of sets of personal data 116 may be the same as the number “N” of thecommunication devices 107. Indeed, each set of personal data 116 maycorrespond to a database record of a client and/or a customer and thelike of an entity associated with the system 100 and/or being managed bycomponents of the system 100, and each communication device 107 may be acommunication device associated with such clients (e.g. a client may bea user of a communication device 107; hence, the terms user and clientare used interchangeably hereafter); however, the number of sets ofpersonal data 116 and the number of communication devices 107 need notbe the same.

Regardless, the database 115 may comprise a database of clients and/orcustomers and the like of an entity associated with the system 100and/or being managed by components of the system 100. Hence, thedatabase 115 may include tens, hundreds, thousands, hundreds ofthousands and/or millions of sets of personal data 116, or more.

Each set of personal data 116 may include personal data of a respectiveclient, and the like, including, but not limited to text correspondingto respective names 117-1 . . . 117-N (interchangeably referred tohereafter, collectively, as the names 117 and, generically, as a name117), text corresponding to respective network addresses 118-1 . . .118-N (interchangeably referred to hereafter, collectively, as thenetwork addresses 118 and, generically, as a network address 118), andthe like.

As depicted, each of the names 117 stored in the personal data 116includes a respective first name of an associated client (e.g. “Bob” and“Sally”), and each of the network addresses 118 stored in the personaldata 116 includes a respective email address name of an associatedclient (e.g. “bob@abc.com” and “sally@123.com”), and the like. However,the personal data 116 may comprise other data associated with the userof the communication device 107, including, but not limited to, textcorresponding to one or more of a name of a company at which the userworks, a home address, a work address, favorite colors and/or otherpersonal preferences, and the like. Furthermore, while the personal data116 is described herein with respect to stored text, the personal data116 may alternatively include graphics, including, but not limited to,an image of an associated client.

Furthermore, each set of personal data 116 may be associated with a userof a communication device 107. For example, a user of the communicationdevice 107-1, associated with the personal data 116-1, may be named“Bob” and have an email address of “bob@abc.com”; a user of thecommunication device 107-2, associated with the personal data 116-2, maybe named “Sally” and have an email address of “sally@123.com”

Furthermore, the personal data 116 may be associated with a user of thecommunication device 107, but not necessarily associated with acommunication device 107. For example, a communication device 107 maycomprise an email application and/or a messaging application and/or avideo application (not depicted) and the like, configured to receive andsend messages associated with an email address stored in the personaldata 116, such an email address may be used to configure an emailapplication and/or a messaging application and/or a video application atany communication device 107. However, the email address is notspecifically associated with a given communication device 107.

In other embodiments, the personal data 116 may be associated with auser of the communication device 107, and/or associated with a specificcommunication device 107 of a user; for example, personal data 116associated with a communication device 107 of a user may include, but isnot limited to, a phone number of a communication device 107, a MAC(Media Access Control) address of a communication device 107, an IP(Internet Protocol) address of a communication device 107, and the like.

Furthermore each set of personal data 116 may be identified using arespective UUID, a respective GUID, and the like, which may be used toidentify a specific set of personal data 116, and/or each name and/ornetwork address and the like in each set of personal data 116 may beidentified using a respective UUID, a respective GUID, and the like.

Attention is next directed to FIG. 2 which depicts a device diagramshowing a device structure of an electronic computing device 200 forreal-time personalization of streaming video according to someembodiments. The device 200 may be, for example, embodied in thecomputing device 101 and/or the video processing devices 105 of FIG. 1,and/or some other computing and/or communication device not illustratedin FIG. 1. Furthermore, the device 200 may be a distributed computingand/or communication device across two or more of the foregoing (ormultiple of a same type of one of the foregoing) and in communicationvia a wired and/or wireless communication connection(s) and/or path(s);in some of these embodiments, the device 200 may be implemented in a ina cloud computing environment.

Furthermore, the communication devices 107 may have a similar devicestructure as the device 200, though adapted for functionality of thecommunication device 107; for example, while the device 200 is depictedwithout a display device, an input device, speakers, microphones,cameras, location determining devices (e.g. a Global Positioning System(GPS) device and the like), the device 200 may include one or more ofsuch components. Hence, while not depicted, the device 200 may furtherinclude one or more input devices, one or more display devices, one ormore speakers, one or more microphones, one or more cameras, one or morelocation determining devices, and/or other types of components.

The device 200 comprises a controller 220, a memory 222 storing one ormore applications 223, and a communication interface 224(interchangeably referred to hereafter as the interface 224)interconnected, for example, using a computer bus. The one or moreapplications 223 are generally used to implement the functionality ofthe device 200; when there are two or more applications 223, suchapplications may be used to implement the functionality of the device200 according to different modes of operation; for example one of theapplications 223 may be used to render real-time personalized video viaweb form requests, while another of the applications 223 may be used torespond to requests via links in email, as described in more detailbelow. For simplicity, the one or more applications 223 will beinterchangeably referred to hereafter as the application 223.

The controller 220 can comprise a processor and/or a plurality ofprocessors, including but not limited to one or more central processors(CPUs) and/or one or more processing units; either way, the controller220 comprises a hardware element and/or a hardware processor. Indeed, insome implementations, the controller 220 can comprise an ASIC(application-specific integrated circuit) and/or an FPGA(field-programmable gate array) specifically configured to implementspecific functionality for real-time personalization of streaming video.Hence, the device 200 is preferably not a generic computing device, buta device specifically configured to implement specific functionality forreal-time personalization of streaming video. For example, the device200 and/or the controller 220 can comprise a computer executable engineconfigured to implement specific functionality for real-timepersonalization of streaming video.

The memory 222 can comprise a non-volatile storage unit (e.g. ErasableElectronic Programmable Read Only Memory (“EEPROM”), Flash Memory) and avolatile storage unit (e.g. random access memory (“RAM”)). Programminginstructions that implement the functional teachings of the device 200as described herein are typically maintained, persistently, in thememory 222 and used by the controller 220 which makes appropriateutilization of volatile storage during the execution of such programminginstructions. Those skilled in the art recognize that the memory 222 isan example of computer readable media that can store programminginstructions executable on the controller 220. Furthermore, the memory222 is also an example of a memory unit and/or memory module and/or anon-volatile memory.

In particular, the memory 222 stores the application 223 that, whenprocessed by the controller 220, enables the controller 220 and/or thedevice 200 to: receive, from a communication device (for example thecommunication device 107), using the communication interface 224, arequest for a personalized video; cause rendering of at least a subsetof the personalized video segments using data for rendering thepersonalized video segments (for example the data 112) and incorporatingpersonal data associated with the request (for example the personal data116); generate, and transmit to the communication device, using thecommunication interface 224, a manifest identifying at least a firstvideo segment selected according to the given order; update, andtransmit to the communication device, using the communication interface224, the manifest to identify, according to the given order, furtheravailable video segments, as rendering of each of the personalized videosegments is completed; and provide, to the communication device, usingthe communication interface 224, as the personalized video, videosegments identified in the manifest, in response to receiving requestsfor the video segments from the communication device.

Hence, it is understood by a person skilled in the art that such amanifest may be used in streaming video, including, but not limited to,streaming video according to the HTTP (Hypertext Transfer Protocol) LiveStreaming (HLS) protocol. Hence, it is further understood by a personskilled in the art that the device 200, and the communication devices107 to which a personalized video is provided, may each be generallyconfigured to operate according to compatible streaming video protocolsthat use manifests to provide such streaming video including, but notlimited to, the HLS protocol.

The communication interface 224 comprises a wired or wireless networkinterface which may include, but is not limited to, any suitablecombination of serial ports, parallel ports, USB ports (Universal SerialBus), and cables therefore, one or more broadband and/or narrowbandtransceivers, such as a cellular network transceiver, a wireless radio,a cell-phone radio, a cellular network radio, a Bluetooth™ radio, a NFC(near field communication) radio, a WLAN (wireless local area network)radio, a WiFi radio (e.g. one or more local area network or personalarea network transceivers operating in accordance with an IEEE 802.11standard (e.g., 802.11a, 802.11b, 802.11g)), a WiMax (WorldwideInteroperability for Microwave Access, operating in accordance with anIEEE 902.16 standard) radio, a packet based interface, anInternet-compatible interface, an analog interface, a PSTN (publicswitched telephone network) compatible interface, and the like, and/or acombination.

Attention is now directed to FIG. 3, which depicts a flowchart of amethod 300 for real-time personalization of streaming video, accordingto non-limiting implementations. In order to assist in the explanationof method 300, it will be assumed that method 300 is performed using thecontroller 220 of the device 200, for example when the controller 220processes the application 223. Indeed, method 300 is one way in whichthe device 200 and/or the controller 220 can be configured. Furthermore,the following discussion of method 300 will lead to a furtherunderstanding of the device 200, and the system 100, and their variouscomponents. However, it is to be understood that the system 100 and/orthe device 200 and/or the controller 220 and/or the method 300 can bevaried, and need not work exactly as discussed herein in conjunctionwith each other, and that such variations are within the scope ofpresent implementations.

Regardless, it is to be emphasized, that the method 300 need not beperformed in the exact sequence as shown, unless otherwise indicated;and likewise, various blocks may be performed in parallel rather than insequence; hence the elements of the method 300 are referred to herein as“blocks” rather than “steps”. It is also to be understood, however, thatthe method 300 can be implemented on variations of the device 200 aswell.

Furthermore, while it is assumed hereafter that the method 300 isperformed at one device 200, the method 300 may be performed at one ormore devices 200, for example at a combination of one or more of thecomputing device 101 and the video processing devices 105.

At a block 302, the controller 220 receives, from a communication device(for example the communication device 107), using the communicationinterface 224, a request for a personalized video.

At a block 304, the controller 220 causes rendering of at least a subsetof the personalized video segments using data for rendering thepersonalized video segments (for example the data 112) and incorporatingpersonal data associated with the request (for example the personal data116 and/or personal data received in the request of the block 302).Rendering of personalized video segments is described in more detailbelow with respect to FIG. 4, FIG. 5 and FIG. 6.

The rendering may be performed in parallel using the video processingdevices 105. For example, the controller 220 may retrieve the data 112and the personal data 116 that is respective to a communication devicethat transmitted the request received at the block 302, and cause therendering of each personalized video segment to occur in parallel usingthe video processing devices 105. Control of the video processingdevices 105 may occur by way of the device 200 retrieving the data 112from the memory 103, and retrieving the personal data 116 to be used inrendering the personalized video segment from the databases 115, andpassing the data 112 and the personal data 116 to the video processingdevices 105. Alternatively, and/or in addition, control of the videoprocessing devices 105 may occur by way of the device 200 providing JSON(JavaScript Object Notation), XML (Extensible Markup Language) and thelike to the video processing devices 105; for example the JSON and/orthe XML may instruct the video processing devices 105 to retrieve thedata 112 and the personal data 115 from locations of the memory 103 andthe database 115. Such JSON and/or XML may be used with UUIDs and/orGUIDs and the like identifying the data 112 and personal data 116 at thememory 103 and/or the database 115. Such UUIDs and/or GUIDs and the likemay be received with the request at the block 302.

When the personalized video segments are rendered in parallel, thecontroller 220 may cause parallel processing resources (e.g. the videoprocessing devices 105) to complete rendering of the personalized videosegments according to the given order. For example, the controller 220may cause the video processing devices 105 to render a respectivepersonalized video segment from the first set of data 112-1 in a mannerthat causes the respective personalized video segment rendered from thefirst set of data 112-1 be completed prior to other personalized videosegments rendered from the other data 112. In other words, as the data112-1 is for rendering a second video segment of the personalized video,the controller 220 may cause the parallel processing resources tocomplete rendering the second segment prior to completing renderingfurther personalized segments.

Furthermore, the personal data used to render a personalized videosegment may be retrieved from the personal data 116 stored in thedatabase (e.g. using a respective network address, UUID, and the like,received with the request of the block 302); for example, in theseembodiments, the request received at the block 302 may include a networkaddress 118 stored in the personal data 116, a UUID identifying thepersonal data 116, and the like, which may be used to retrieve acorresponding name 117, and the like, from the personal data 116, forexample in a database look-up process, and the like. For example, inthese embodiments, a message, such an email, and the like, may betransmitted to a communication device, the message including a link forinitiating a request for a personalized video from the device 200; whenthe link is actuated, the request may be transmitted to the device 200(e.g. via an associated network address in the link), the requestincluding a network address of the communication device, UUIDs and/orGUIDs, and the like, identifying the personal data 116 to be used whengenerating a personalized video, and/or the segments 111 and/or the data112 to be used when generating a personalized video. Furthermore, suchUUIDs and/or GUIDs, and the like may be included in the messagetransmitted to the communication device.

Alternatively, the personal data used to render a personalized videosegment may be received with the request of the block 302; for example,in these embodiments, the request received at the block 302 may includetext corresponding to a name to be used to render the personalized videosegments and/or a graphic (e.g. an image of a user) to be used to renderthe personalized video segments. In these embodiments, for example, auser of a communication device transmitting a request may fill out aform, such as a webform, and the like, requesting a personalized video,the form including fields for receiving personal data to be used torender a personalized video, such as a name, an image, and the like; theform may further include a virtual button, a link, and the like, forinitiating a request for a personalized video from the device 200; whenthe virtual button, the link, and the like, is actuated, the request maybe transmitted to the device 200 (e.g. via a network address associatedwith the virtual button), the request including the personal data to beused to render a personalized video. Alternatively, the webform mayinclude code, such as javascript and the like, which causes datareceived in fields to be pre-submitted to the device 200; such a webformmay comprise a multi-stage webform, and the like, the data from which isfully submitted when the virtual button, the link, and the like, isactuated.

At a block 306, the controller 220 generates, and transmits to thecommunication device, using the communication interface 224, a manifestidentifying at least a first video segment selected according to thegiven order. The manifest may comprise a link, such as a URL (UniformResource Locator), and the like, to the first video segment. Forexample, with reference to FIG. 1, a link in the manifest may include aURL to the first nonpersonalized video segment 111-1 as stored in thememory 103; alternatively, the first nonpersonalized video segment 111-1may be retrieved by the device 200 and temporarily stored at a memory ofthe device 200 (e.g. at the memory 222) and a link to the firstnonpersonalized video segment 111-1 stored at the device 200 may beprovided in the manifest.

In some embodiments, as depicted in FIG. 1, the first video segment isthe nonpersonalized video segment 111-1. Indeed, the personalized videoto be provided may be specifically selected such that the first videosegment is a prerendered nonpersonalized video segment so that the firstvideo segment is immediately available to be provided to the requestingcommunication device.

However, the first video segment may alternatively be a personalizedvideo segment to be rendered from a set of data 112. Hence, when therequest is received at the block 302, rendering of the first videosegment is initiated and the manifest identifying at least the firstvideo segment may be transmitted whether the first video segment hascompleted rendering, or not. In these embodiments, the link to the firstvideo segment may be a link and/or URL to a personalized video segmentthat is not yet available. However, when the rendering of the firstvideo segment is complete, the controller 220 associates the completedfirst video segment with the link to the first video segment in themanifest.

At a block 308, the controller 220 determines whether rendering of apersonalized video segment is complete, for example a next personalizedvideo segment according to the given order. When rendering of apersonalized video segment is not complete (a “NO” decision at the block308), the controller 220 continues to monitor for completion ofrendering of a personalized video segment at the block 308.

When rendering of a personalized video segment is complete (a “YES”decision at the block 308), at a block 310, the controller 220 updates,and transmits to the communication device, the manifest to identify,according to the given order, further available video segments. Forexample, each instance of a next personalized video segment iscompleted, according to the given order, the manifest is updated toidentify the next personalized video segment, as well as any prerenderednonpersonalized video segments 111 that follow the next personalizedvideo segment. Furthermore, when the manifest is updated to identify alast video segment in the personalized video, the manifest may beupdated to identify that no further segments will be added (for example,an HLS manifest may include an “ENDLIST” indicator), and the like.

At a block 312, the controller 220 determines whether a request forvideo segments is received from the communication device. When a requestfor the video segments is not received from the communication device (a“NO” decision at the block 312), the controller 220 continues to monitorfor completion of rendering of a personalized video segment at the block308.

When a request for the video segments is received from the communicationdevice (a “YES” decision at the block 312), at a block 314, thecontroller 220 provides, to the communication device, as thepersonalized video, video segments identified in the manifest, inresponse to receiving requests for the available video segments from thecommunication device.

In general, requests for video segments received from the communicationdevice may comprise the links to video segments provided in themanifest, and a communication device requesting the video segmentsgenerally requests the video segments in the order of the links in themanifest, which is generally the given order of the nonpersonalizedvideo segments and the personalized video segments. Hence, for example,a communication device receiving a manifest may request the videosegments using the links in the manifest requested in the order of thelinks in the manifest (e.g. a video segment associated with a first linkis requested first, a video segment associated with a second link isrequested second, etc.).

In embodiments where the request for the video segments received fromthe communication device is for the first video segment (e.g. the linkto the first video segment), and the first video segment is aprerendered nonpersonalized video segment, such as the nonpersonalizedvideo segment 111-1, the controller 220 transmits and/or streams thefirst video segment upon receiving the request.

However, in embodiments where the request for the video segmentsreceived from the communication device is for the first video segment,and the first video segment is a personalized video segment whererendering is not yet completed, the controller 220 may transmit an errormessage (e.g. a “404 Not Found” error message, and the like) to therequesting communication device. At communication devices operatingaccording to some streaming protocols, receipt of such an error messagecauses a communication device to again request the video segment thatcaused the error message. Alternatively, when a requested video segmentis not received within a given time period, and the like, thecommunication device requesting the video segment will resubmit therequest for the video segment until received and/or a timeout occurs;indeed, communication devices configured to operate in this manner willcontinue to request video segments until it is identified that nofurther video segments are available (e.g. the HLS “ENDLIST” identifierin the manifest is reached). Hence, this process may automaticallycontinue between the controller 220 and the requesting communicationdevice until rendering of the personalized video segment is complete andthe controller 220 provides the personalized video segment to thecommunication device.

At a block 316, the controller 220 determines whether all video segmentsin the personalized video have been provided to the communicationdevice. When all video segments in the personalized video have not yetbeen provided to the communication device (a “NO” decision at the block316), the controller 220 may repeat one or more of the blocks 308, 310,312, 314.

However, the controller 220 generally stops executing the blocks 308,310 once rendering of all the personalized video segment is complete,but continues to monitor for requests at the block 312, presuming notall video segments in the personalized video have been provided to thecommunication device. Indeed, once rendering of all the personalizedvideo segment is complete a “NO” decision at the block 312 may result inthe block 312 being repeated by the controller 220 until a request isreceived (e.g. a “YES” decision at the block 312). Once all theavailable video segments are provided (a “YES” decision at the block316), the controller 220 ends the method 300 at a block 318.

While the method 300 has been described with respect to eachpersonalized video segment being rendered independent of one another, insome embodiments the controller 220 determines whether any portionsand/or layers and/or content of previously rendered personalized videosegments are shared with personalized video segments to be rendered, forexample by “pre-processing” the data 112 and/or the personal data 116 todetermine personalized video segments that share content; such“pre-processing” the data 112 and/or the personal data 116 may occurwhen the request for the personalized video is received at the block302, prior to rendering at least a subset of the personalized videosegments at the block 304 and/or receiving requests for video segmentsat the block 312. Such pre-processing may include comparing a set ofdata 112 with the other sets of data 112 to determine portions and/orlayers and/or content that are shared.

When personalized video segments share any portions and/or layers and/orcontent, such shared content may be rendered once, for example whenrendering a first personalized video segment that includes the sharedcontent, and reused when rendering later personalized video segment thatincludes the shared content. In some of these embodiments, somepersonalized video segments may be the same as each other (e.g.respective data 112 is the same for each of a plurality of personalizedvideo segments) and such personalized video segments may be renderedonce and provided at the block 314 each time a request is received, atthe block 312, for a personalized video segment that is the same as apreviously rendered personalized video.

Prior to discussing example embodiments of the method 300, rendering ofpersonalized video segments at the block 304 is described with respectto FIG. 4, FIG. 5, and FIG. 6. A person of skill in the art willunderstand that in FIG. 4, FIG. 5 and FIG. 6, rendering of personalvideo segments may occur at one or more of the video processing devices105 using, for example, any suitable application for rendering personalvideo segments, which may include components of the application 223and/or another application.

Attention is next directed to FIG. 4 which depicts an example set ofdata 112 comprising: prerendered static layers 401-1, 401-2, 401-3(interchangeably referred to hereafter, collectively, as the prerenderedstatic layers 401 and, generically, as a prerendered static layer 401)and prerendered non-static layers 402-1, 402-2, 402-3 (interchangeablyreferred to hereafter, collectively, as the prerendered non-staticlayers 402 and, generically, as a prerendered non-static layer 402).Each of the layers 401, 402 may comprise a respective layer of one ormore frames of a personalized video segment. While example embodimentsare described with respect to a personalized video segment having threeframes, a personalized video segment may comprise any number of frames.

For example, the personalized video segment to be rendered using theexample data 112 depicted in FIG. 4 comprises three frames, with theprerendered static layers 401 being a static layer of each of the threeframes. For example, the prerendered static layer 401 includes objects(e.g. as depicted trees) which do not generally move from frame toframe, other than, for example, small differences therebetween (e.g. thetrees subtly moving with wind, and the like; indeed, regardless of thecontent of the prerendered static layers 401 being strictly static ornot, frames in videos tend to change, even for static content). Whilethree prerendered static layers 401 are depicted (e.g. one for eachframe), in other embodiments, one prerendered static layer 401 may beprovided, which is used for each frame (e.g. the same layer may beincorporated into each of the three frames).

The three prerendered non-static layers 402 may each comprise arespective non-static layer of each of the three frames (e.g. theprerendered non-static layer 402-1 is a non-static layer of the firstframe, the prerendered non-static layer 402-2 is a non-static layer ofthe second frame, and prerendered non-static layer 402-3 is a non-staticlayer of the third frame). Each of the non-static layers 402 include,for example, a moving object (e.g. as depicted a person holding awhiteboard, a sign, and the like, and referred to hereafter as a“whiteboard”) which moves from frame to frame; as such the moving objectin each of the non-static layers 402 has had a transformation applied sothat the moving object has a “blur” (represented by dotted lines) fromthe first frame to the second frame to the third frame.

In general, each of the layers 401, 402 have been prerendered and storedin the example data 112.

However, a personalized layer has not yet been rendered. As such, theexample data 112 depicted in FIG. 4 further includes personalizablelayers 403-1, 403-2, 403-3 (interchangeably referred to hereafter,collectively, as the personalizable layers 403 and, generically, as apersonalizable layer 403) each of which includes a respective field404-1, 404-2, 404-3, and the like (interchangeably referred tohereafter, collectively, as the fields 404 and, generically, as a field404). Each of the fields 404 may be populated with personal data (forexample a name 117 and/or text (not shown) from the personal data 116and/or a graphic (not shown) stored in the personal data, and/or textand/or a graphic received with a request from a communication device),when rendering a personalized layer from each of the personalizablelayers 403. In other words, each of the personalizable layers 403 areused to render a respective personalized layer for each of the frames

In some embodiments a position of a field 404 may be static from layerto layer (e.g. the personal data does not move from frame to frame); inthese embodiments, only one personalizable layer 403 may be provided andused to render one personalized layer to be used in all the frames.

However, as depicted, the field 404 moves from layer to layer; in otherwords, in each of the personalizable layers 403, a respective field 404is in a different position. Hence, the data 112 further includestransformation data 405-1, 405-2, 405-3 (interchangeably referred to,hereafter, collectively as the transformation data 405 and, generically,as a set of transformation data 405) which may comprise an algorithmand/or data for transforming the personalized data in the respectivefields 404 for each respective personalizable layer 403, for examplewhen rendering a respective personalized layer. For example, such arespective personalized layer (e.g. rendered from each of thepersonalizable layers 403) may be transformed according to one or moreof a previous respective personalized layer and a next respectivepersonalized layer. In particular, the set of transformation data 405-1is for transforming personalized data in the fields 404-1 of thepersonalizable layer 403-1, the set of transformation data 405-2 is fortransforming personalized data in the fields 404-2 of the personalizablelayer 403-2, and the set of transformation data 405-3 is fortransforming personalized data in the fields 404-3 of the personalizablelayer 403-3. The transformation data 405 may indicate how text and/orgraphics of personal data in a respective field 404 is to be transformedin each of personalized layers to better render movement of the textand/or graphics of personal data between the frames, and/or to customizethe text and/or graphics for rendering onto an object in the non-staticlayers 402 (e.g. for example the transformation data 405 may be forwarping and/or shaping the text and/or graphics for compatibility withthe object). Non-limiting examples of such transformation data 405include, but are not limited to, any algorithms and/or data for blurringtext and/or graphics opposite a direction of movement from frame toframe. Furthermore, each set of transformation data 405 may be generatedwhen the layers 403 are generated. In some embodiments, a set oftransformation data 405 may comprise an empty set and/or may not bepresent, for example when no transformation is to occur for a givenfield 404 (e.g. when a field 404 doesn't move from frame to frame).

Furthermore, while positions of the fields 404 are depicted as beingcoupled with movement of the objects in the non-static layers 402 (e.g.such that a field 404 aligns with a position of the whiteboard, in thenon-static layers 402), positions of the fields 404 may be decoupledwith the positions of the objects in the non-static layers 402. As willbe described below, a name of a client from personal data may berendered on the whiteboard of the non-static layers 402, with thepositions and sizes of the fields 404 being similar to the sizes ofwhiteboard in the non-static layers 402; however, a name of a client mayalternatively move independent of the whiteboard.

Furthermore, the example data 112 of FIG. 4 may include any additionaldata for rendering the personal data (which may be stored in thetransformation data 405), including, but not limited to, a font to beused with text, a size of the text, a color of the text, a backgroundcolor of the text, and the like. For example, when a name of a client isto be rendered on the whiteboard of the non-static layers 402, the data112 may include additional data indicating that the font for the name isto be of a size that fits the name onto the whiteboard, with a colorthat is different from that of the whiteboard and a background colorthat is transparent and/or a similar color of the whiteboard.Furthermore, the text size may be variable, for example to “fit” thename onto the whiteboard, with shorter names being rendered in a largefont relative to longer names rendered in a smaller font. Furthermore,while the example “whiteboard” of the non-static layers 402 is flat, inother embodiments an object of the non-static layers 402 onto whichpersonal data may be rendered may be curved with the personal datawarped and/or transformed accordingly (e.g. as stored in thetransformation data 405). Furthermore, in some embodiments, in someframes the text and/or graphics of the personal data used in the fields404 may be partially occluded, for example when a “person” and/oranother object moves “in front” of the object onto which the personaldata is rendered; data for rendering the personal data in the fields 404when such occlusion occurs may be stored in the transformation data 405.

Attention is next directed to FIG. 5 which depicts an example renderingof respective personalized layers 503-1, 503-2, 503-3 (interchangeablyreferred to, hereafter, collectively, as the personalized layers 503and, generically, as a personalized layer 503) of each of three frames,from: the personalizable layers 403, the name 117-1 of the personal data116-1, and the transformation data 405. The rendering depicted in FIG. 5may be performed by one or more of the video processing devices 105.

In particular, the name “Bob” is inserted into each of the fields 404 torender a respective personalized layer 503 of each of the three frames,with the transformation data 405 used to “blur” the name “Bob” (theblurring represented by broken lines), opposite a direction of movementof the name “Bob” between the personalized layers 503. For example, thename “Bob” is moving up and to the right from the personalized layer503-1 to the personalized layer 503-2, hence, the name “Bob” is blurreddown and to the left in the personalized layer 503-2, the transformationdata 405-2 defining such blurring; similarly, the name “Bob” continuesto move up and to the right from the personalized layer 503-2 to thepersonalized layer 503-3, hence the name “Bob” is blurred down and tothe left in the personalized layer 503-3, the transformation data 405-3defining such blurring. As the name “Bob” appears to be moving fasterbetween the personalized layers 503-2, 503-3, then compared to betweenthe personalized layers 503-1, 503-2, there may be more blurring in thepersonalized layer 503-3, as compared to the personalized layer 503-2(e.g. as depicted), as defined in the transformation data 405. As thename “Bob” is initially still and/or static in the personalized layer503-1, the transformation data 405-1 may be omitted and/or may be anempty set, and/or may define blurring that may be provided in thepersonalized layer 503-1 that corresponds to any blurring in thecorresponding non-static layer 403-1.

Attention is next directed to FIG. 6 which depicts rendering of exampleframes 601-1, 601-2, 601-3 of a personalized video segment from theexample layers 401, 402, 503 of FIG. 4 and FIG. 5. The frames 601-1,601-2, 601-3 are interchangeably referred to, hereafter, collectively,as the frames 601 and, generically, as a frame 601.

The rendering depicted in FIG. 6 may be performed by one or more of thevideo processing devices 105.

In particular, in FIG. 6 a first frame 601-1 is rendered by combing thefirst prerendered static layer 401-1 with the first prerenderednon-static layer 402-1 and the first personalized layer 503-1, forexample by flattening the three layers 401-1, 402-1, 503-1 into theframe 601-1. Similarly, a second frame 601-2 is rendered by combing thesecond prerendered static layer 401-2 with the second prerenderednon-static layer 402-2 and the second personalized layer 503-2, forexample by flattening the three layers 401-2, 402-2, 503-2 into theframe 601-2. Similarly, a third frame 601-3 is rendered by combing thethird prerendered static layer 401-3 with the third prerenderednon-static layer 402-3 and the third personalized layer 503-3, forexample by flattening the three layers 401-3, 402-3, 503-3 into theframe 601-3. The frames 601 may then be combined to form a personalizedvideo segment 612.

In yet further embodiments, the respective layers 401, 402 for eachframe 601 may be combined and stored in the data 112, for example, whengenerating the data 112. In other embodiments, the respective layers401, 402 for each frame 601 may be combined while the personalizedlayers 503 are being generated. In yet further embodiments, more layersmay be added to the frames 601 including, but not limited to, layerswhere objects occlude the personalized data, such layers being “on top”of the personalized layers 503. In yet further embodiments, when themovement of personalized data is decoupled from the movement of objectsin the non-static layers 402, and the objects in the non-static layers402 are to occlude the personalized data in the personalized layers 503,one or more of the non-static layers 402 (e.g. the non-static layers 402that provide such occlusion), maybe “on top” of the personalized layers503. Indeed, the various layers of the frames 601 may be combined in anysuitable manner, with data 112 including data defining an order of thelayers when combining into the frames 601.

While rendering of the personalized video segment 612 is described withrespect to one field 404 in the personalizable layers 403, thepersonalizable layers 403 may include more than one field 404, forexample for including other text and/or graphics from the personal data116 including, but not limited to, names of companies and the like.Furthermore, other data from the personal data 116 may be used tocustomize text and/or graphics incorporated into the fields 404including, but not limited, to favorite colors, and the like, from thepersonal data 116; for example, the text “Bob” of the name 117-1 may berendered in a color stored in the personal data 116-1 as a favoritecolor.

FIG. 4, FIG. 5 and FIG. 6 hence show an example embodiment of the block304 in which rendering of a personalized video segment occurs by:retrieving, from the data 112 for rendering personalized video segments,one or more of a respective prerendered static layer and a respectiveprerendered non-static layer; rendering a respective personalized layerusing the personal data; and combining one or more of the respectivepersonalized layer and the respective prerendered non-static layer.

Similarly, FIG. 4, FIG. 5 and FIG. 6 further show an example embodimentof the block 304 in which rendering of a personalized video segmentoccurs by: retrieving, from the data 112 for rendering personalizedvideo segments, transformation data; and rendering the respectivepersonalized layer using the personal data, and according to thetransformation data, such that the respective personalized layer istransformed according to one or more of a previous respectivepersonalized layer and a next respective personalized layer.

Techniques similar to those described with respect to FIG. 4, FIG. 5 andFIG. 6 may also be used to render a personalized icon using text and/orgraphics stored in the personal data 116, one or more of the layers 401,402 and the icon data 113. For example, attention is next directed toFIG. 7 which depicts rendering of a personalized icon 701. Inparticular, an example of the icon data 113 includes a “Play” symbol(e.g. a triangle which may represent a virtual button for “playing” avideo”) and a field 704 on the symbol which may be populated, asdepicted, with the name 117-2, similar to as described above withrespect to the fields 404 being populated by the name 117-1. Asdepicted, a video processing device 105 and/or the computing device 101(e.g. the device 200 implementing one or more of the applications 223)may combine the layer 401 (and/or one or more of the layers 402) withthe icon data 113 with the field 704 populated with the name 117-2, torender the personalized icon 701. As depicted, the personalized icon 701includes the name “Sally” appearing on the “Play” symbol with the imageof the prerendered static layer 401 used as a background. Thepersonalized icon 701 may be temporarily stored in a memory of thesystem 100 and/or incorporated into an email, message and the liketransmitted to a communication device 107 of the client associated withthe name 117-2, along with an associated link for requesting apersonalized video. Alternatively, the personalized icon 701 may berendered without the icon data 113 or without the one or more of thelayers 401, 402.

The method 300 is next described with respect to FIG. 8 to FIG. 13, eachof which are substantially similar to FIG. 1 with like elements havinglike numbers. A person of skill in the art will understand that in FIG.8 to FIG. 13, a controller of the computing device 101 is implementingthe application 223 and/or that in FIG. 8 to FIG. 13 the device 200 isembodied in the computing device 101 and/or that the controller 220 ofthe device 200 is embodied in a controller of the computing device 101.

Attention is next directed to FIG. 8 which depicts example embodimentsof the block 302 of the method 300.

In the depicted example embodiment, the computing device 101 isreceiving (e.g. at the block 302 of the method 300) a request 801 for apersonalized video from the communication device 107-1. For example, asdepicted, a webform 810 is being provided at the communication device107-1 (e.g. at a display device thereof), for example in a browserapplication; in particular, a user of the communication device 107-1 maybe browsing the Internet and load the webform 810 into a browser due toan interest in a product, service, and the like being provided by anentity associated with the nonpersonalized video segments 111 and thedata 112. The user may use the webform 810 to request a personalizedvideo. Such a user may or may not have a pre-existing relationship withan entity providing the webform 810 and hence data of the user may ormay not be stored in the personal data 116.

As depicted, the webform 810 includes a field 811 for inputting a name(e.g. “Bob”), for example using an input device of the communicationdevice 107-1, and/or a field 812 for inputting an email address (e.g.“bob@abc.com”). The webform 810 further includes an optional virtualbutton 813, and the like, which, when actuated, (e.g. using an inputdevice of the communication device 107-1) causes the communicationdevice 107-1 to transmit the request 801 to the computing device 101,with the name and the email address entered in the respective fields811, 812. The request 801 may further include a rendered version of thewebform 810 with the fields 811, 812 “filled in” with the name and theemail address. The optional virtual button 813 is hence associated witha network address of the computing device 101 such that the request 801is automatically transmitted to the computing device 101 when theoptional virtual button 813 is actuated. However, any actuatable link,and the like, may be used in place of the virtual button 813 and/or thewebform 810 may submit data entered in the fields 811, 812 as enteredand automatically transmit the request 801 without actuation of avirtual button, a link, and the like, in the webform 810 (indeed, inthese embodiments, an actuatable virtual button, link, and the link maynot be present in the webform 810).

The request 801 may further include a file type (e.g. MPEG2TS, MP4, andthe like), a frame rate, a resolution and the like of a personalizedvideo being requested.

The request 801 may further comprise one or more identifiers of thepersonalized video to be generated, for example one or more UUIDs,GUIDs, and the like identifying the segments 111 and the data 112; suchUUIDs and/or GUIDs, and the like may be incorporated into the webform810.

As also depicted in FIG. 8, the request 801 is received at the computingdevice 101 and personal data such as a name 817 (e.g. “Bob”) and anemail address 818 (e.g. “bob@abc.com”) is extracted from the request801. Alternatively, the email address 818 may be used to extract thename 117-1 from the personal data 116-1 for example using a databaselookup and the like (presuming that the user of the communication device107-1 has a pre-existing relationship with an entity providing thewebform 810). In other words, as depicted, the name 817 is the same asthe name 117-1 and the email address 818 is the same as the networkaddress 118-1.

However, in other embodiments, there need not be a corresponding set ofpersonal data 116 for the email address 818; rather, the personal dataused to render a personalized video may be received via the request 801without a database lookup and the like.

Furthermore, a person of skill in the art will further understand thatthe webform 810 and the request 801 are specifically for requesting apersonalized video to be generated from the nonpersonalized videosegments 111 and the data 112. When the memory 103 stores other sets ofnonpersonalized video segments and the data for rendering personalizedvideo segments, other webforms may be used to request personalizedvideos from those other sets. Hence, the request 801 may include anidentifier identifying the personalized video to be generated from thenonpersonalized video segments 111 and the data 112.

Attention is next directed to FIG. 9 which depicts example embodimentsof the block 304 and the block 306 of the method 300.

As depicted, the computing device 101 has retrieved the nonpersonalizedvideo segments 111 and the data 112 from the memory 103, for example inresponse to receiving the request 801. While the present exampleembodiment is described with respect to the computing device 101 havingretrieved the nonpersonalized video segments 111 and the data 112 fromthe memory 103, the computing device 101 may alternatively not retrievethe nonpersonalized video segments 111 and the data 112 from the memory103 but rather control the various components of the system 100 toretrieve data from the memory 103 using JSON and/or XML (each of whichmay use UUIDs, GUIDs and the like to identify data from the memory 103and/or the database 115), and the like, and/or using links to thenonpersonalized video segments 111 and the data 112 from the memory 103as stored in the memory 103.

As further depicted in FIG. 9, the computing device 101 is providing(e.g. at the block 304 of the method 300) at least the data 112-1 to thefirst video processing device 105-1 along with the name 817 (e.g. thedata to be used to render a respective personalized video segment)and/or an identifier (e.g. a link) of the name 817 in a rendered versionof the webform 810 received, for example, in the request 801 (which maybe temporarily stored at a memory of the computing device 101, thememory 103 and/or the database 115 and/or another memory). Similarly,the computing device 101 is providing (e.g. at the block 304 of themethod 300) the data 112-2 to the video processing device 105-M alongwith the name 817. Each of the video processing devices 105 proceed torender a respective personalized video segment as described above withrespect to FIG. 4, FIG. 5 and FIG. 6, using the text “Bob”.

While as depicted only the first two sets of data 112-1, 112-2 areprovided to the video processing devices 105 to render a first twopersonalized video segments (e.g. in parallel), in other embodiments,all the data 112 may be provided to respective video processing devices105 to render all the personalized video segments (e.g. in parallel),assuming that the number “M” of video processing devices 105 is greaterthan or equal to the number “4” of sets of data 112. When the number “M”of video processing devices 105 is less than the number “4” of sets ofdata 112, the computing device 101 may generally cause parallelprocessing resources (e.g. the video processing devices 105) to completerendering of the personalized video segments according to the givenorder such that rendering of the first personalized video segment (fromthe data 112-1) is completed at least first, rendering of the secondpersonalized video segment (from the data 112-2) is completed at leastsecond, etc. However, generally, the computing device 101 may generallycause parallel processing resources (e.g. the video processing devices105) to render all the personalized video segments concurrently.

As further depicted in FIG. 9, the computing device 101 is generating arespective link 901-1, 901-2, 901-3, 901-4, 901-5, 901-6, 901-7, 901-8,901-9 which identifies each of the respective nonpersonalized videosegments 111 and personalized video segments to be rendered from eachset of the data 112 and the name 817. The links 901-1, 901-2, 901-3,901-4, 901-5, 901-6, 901-7, 901-8, 901-9 are interchangeably referred tohereafter, collectively, as the links 901 and, generically, as a link901.

Each link 901 may identify a respective video segment using a URL to arespective video segment. For example, the link 901-1 may comprise alink and/or a URL to the nonpersonalized video segment 111-1, asretrieved from the memory 103 or as stored in the memory 103, the link901-2 may comprise a link and/or a URL to a personalized video segmentthat is being rendered by the video processing device 105-1 from thedata 112-1 and the name 817, etc. In some embodiments, the link 901-1may be encrypted and/or signed with a cryptographic key (e.g. previouslyprovided to the communication device 107-1, for example when the request801 is received), and the like; in other words, encryption and/orsigning schemes may be used when exchanging data between the computingdevice 101 and the communication devices 107. Alternatively, the link901-2 may not be generated until the personalized video segment that isbeing rendered by the video processing device 105-1 from the data 112-1and the name 817 is complete. Similarly, links 901 to other personalizedvideo segments to be rendered by the video processing device 105-1 fromthe data 112 and the name 817 may not be generated until respectiverendering is complete.

However, the links 901 to all the video segments to be provided to thecommunication device 107-1 may be generated when the request 801 isreceived and/or before rendering of the personalized video segmentsbegins; indeed, generation of the links 901 may include pre-processingof the data 112 and/or the personal data 116 to determine personalizedvideo segments (yet to be generated) that share content, suchpre-processing used to reduce redundant generation of at least portionsof the personalized video segments. Furthermore, when the links 901 aregenerated, before rendering of the personalized video segments begin, amemory location is allocated for storing each of the personalized videosegment associated with the links 901 (e.g. a memory location at thecomputing device 101, the memory 103, the database 115 and/or anothermemory).

As depicted, the computing device 101 has associated links 901, thatidentify personalized video segments to be rendered, with respectivedata 112, though such an association may be used as a placeholder untilthe respective personalized video segments are rendered, and/or such anassociation may not occur, and some other placeholder may be used.

As depicted, the computing device 101 generates (e.g. at the block 306of the method 300) a manifest 903 identifying at least a first videosegment selected according to the given order and, in particular, thelink 901-1 which identifies the first nonpersonalized video segment111-1. The manifest 903 does not include the link 901-2 as rendering ofthe respective personalized video segment is not yet complete. Indeed,the computing device 101 omits links 901 to other video segments thatfollow the link 901-2 to ensure that the respective video segments arenot requested out of the given order.

Also depicted in FIG. 9, the computing device 101 transmits (e.g. at theblock 306 of the method 300) the manifest 903, including the link 901-1,to the communication device 107-1 from which the request 801 wasreceived.

Hence, FIG. 8 and FIG. 9 depict example embodiments of the block 306where a first available video segment, according to the given order, isa first nonpersonalized video segment, and the controller 220 of thedevice 200 and/or the computing device 101 is further configured to: inresponse to receiving a request, transmit a manifest identifying thefirst nonpersonalized video segment.

However, in embodiments where a first available video segment, accordingto the given order, is a personalized video segment, and the controller220 of the device 200 and/or the computing device 101 may be furtherconfigured to: in response to receiving a request, transmit a manifestidentifying the first personalized video segment before rendering of thefirst personalized video segment is complete; and, when a request forthe first personalized video segment is received prior to the renderingof the first personalized video segment being complete, return a messagethat prompts the communication device 107-1 to again request the firstpersonalized video segment.

Attention is next directed to FIG. 10 which depicts example embodimentsof the block 308, the block 310, the block 312 and the block 314 of themethod 300.

As depicted, each video processing device 105-1, 105-M has completedrendering of a respective personalized video segment 1012-1, 1012-2(e.g. the personalized video segment 1012-1 was rendered from the data112-1 and the name 817, and the personalized video segment 1012-2 wasrendered from the data 112-2 and the name 817). The respectivepersonalized video segments 1012-1, 1012-2 are generally rendered asdescribed with respect to FIG. 4, FIG. 5 and FIG. 6. As also depicted inFIG. 10, each video processing device 105-1, 105-M is providing thepersonalized video segments 1012-1, 1012-2 (interchangeably referred tohereafter, collectively, as the personalized video segments 1012 and,generically, as a personalized video segment 1012) to the computingdevice 101.

In response the computing device 101 determines (e.g. a “YES” decisionat the block 308) that rendering of a personalized video segment 1012 iscomplete generates (e.g. at the block 310) an updated manifest 1023(e.g. the manifest 903 is updated to the manifest 1023) to include thelinks 901-2, 901-3, 901-4, 901-5, 901-6. For example the links 901-2,901-3 identify the respective personalized video segments 1012-1, 1012-2and/or the computing device 101 associates the links 901-2, 901-3 withthe personalized video segments 1012-1, 1012-2; indeed, in the depictedexample, the data 112-1, 112-2 is replaced with the personalized videosegments 1012-1, 1012-2 in the association with the links 901-2, 901-3(though such a replacement is illustrative and the initial associationwith the data 112-1, 112-2 with the links 901-2, 901-3 may not haveoccurred and/or may have been used as placeholder and/or another type ofplaceholder may have been used).

However, the manifest 1023 further includes the links 901-4, 901-5,901-6 that identify nonpersonalized video segments 111-2, 111-3, 111-4that occur between the personalized video segment 1012-2 and anotherpersonalized video segment that is still being rendered and/or that isstill to be rendered (e.g. a personalized video segment rendered fromthe data 112-3). In other words, the updated manifest 1023 includes allavailable video segments. Put another way, as rendering of a nextpersonalized video segment is completed, the computing device 101updates a manifest to identify the next personalized video segment andany nonpersonalized video segments that occur between the nextpersonalized video segment and another personalized video segment thatis still being rendered (and/or that is still to be rendered).

As also depicted in FIG. 10, the computing device 101 is transmitting(e.g. at the block 310) the updated manifest 1023 to the communicationdevice 107-1.

Furthermore, in FIG. 10, the communication device 107-1, having receivedthe link 901-1 with the manifest 903 is transmitting a request 1031 forthe first nonpersonalized video segment 111-1 by including the link901-1 in the request 1031. The request 1031 may be generated using astreaming video application at the communication device 107-1, which maybe provided in the same browser application used to provide the webform810; such streaming video application generally use manifests, such asthe manifest 903, to manage and request segments of a streaming video ina given order using links in the manifest.

Hence, the computing device 101 receives the request 1031 (e.g. at theblock 312 of the method 300) and, in response, provides (e.g. at theblock 314 of the method 300), the nonpersonalized video segment 111-1 tothe communication device 107-1. For example, the computing device 101may stream the nonpersonalized video segment 111-1 to the communicationdevice 107-1, as previously retrieved from the memory 103 and/or fromthe memory 103 and/or by retrieving the nonpersonalized video segment111-1 from the memory 103 when not previously retrieved. As thenonpersonalized video segment 111-1 is received at the communicationdevice 107-1, the communication device 107-1 “plays” the nonpersonalizedvideo segment 111-1, for example using a streaming video application.

While in FIG. 10 the updated manifest 1023 is depicted as beingtransmitted prior to the nonpersonalized video segment 111-1, themanifest 1023 and the nonpersonalized video segment 111-1 may betransmitted in any order; for example, when the request 1031 is receivedat the computing device 101 prior to the personalized video segment1012-1, 1012-2 being complete, the nonpersonalized video segment 111-1may be transmitted prior to the updated manifest 1023.

In general, the computing device 101 continues to update the manifestused to provide video segments to the communication device 107-1 asrendering of the personalized video segments is completed. For example,attention is next directed to FIG. 11 which depicts the computing device101 continuing to cause rendering of personalized video segments usingthe data 112-3, 112-4 provided to the video computing devices 105, withthe name 817, to render respective personalized video segments.

Also depicted in FIG. 11, the communication device 107-1 continues torequest video segments using the updated manifest 1023 via a request1131 that includes the link 901-2 to the next video segment in the givenorder, and the computing device 101 continues to provide the respectivenext video segment to the communication device 107-1, specifically thepersonalized video segment 1012-1. In other words, as depicted, thecomputing device 101 continues to render personalized video segmentsthat occur later in the personalized video, according to the givenorder, while providing, to the communication device 107-N, thepersonalized video segments that occur earlier in the personalizedvideo, as they are completed.

Similarly, as depicted in FIG. 12, when personalized video segments1212-3, 1212-4, rendered respectively from the data 112-3, 112-3, arecompleted by the video processing devices 105, an updated manifest 1223is produced to include the respective links 901-7, 901-9 to thepersonalized video segments 1212-3, 1212-4, in the given order, as wellas the link 901-8 to the nonpersonalized video segment 111-5 therebetween. The updated manifest 1223 is transmitted to the communicationdevice 107-1, which continues to request the video segments of thepersonalized video segment according to the updated manifest 1023(and/or the updated manifest 1223) via a request 1231 which, asdepicted, includes the link 901-3 to the personalized video segment1012-2.

When rendering of all the personalized video segments 1012-1, 1012-3,1212-3, 1212-4 have been completed, the block 308 and the block 310 ofthe method 300 are no longer implemented, though the computing device101 continues to implement the block 312 and the block 314 until all thevideo segments of the personalized video are provided to thecommunication device 107-1 (e.g. a “YES” decision at the block 316 suchthat the method 300 ends at the block 318).

While not depicted, it is further understood by a person of skill in theart that the computing device 101 and/or the video processing devices105 may further convert any video segments (including thenonpersonalized video segments 111) to a file type, a frame rate and/ora resolution received in the request. When such conversions are tooccur, the computing device 101 may control the video processing devices105 in a manner that causes the first video segment to be convertedbefore other video segments.

In addition, while present embodiments are described with respect to thepersonalized video segments being rendered, in parallel, two at a time,all the personalized video segments may be rendered concurrently and/orin parallel when the video processing devices 105 are available to doso.

Attention is next directed to FIG. 13 which depicts the system 100 afterthe personalized video described with respect to FIG. 8, FIG. 9, FIG.10, FIG. 11 and FIG. 12 has been provided to the communication device107-1. In particular a copy of the personalized video is not stored inthe system 100; rather, the nonpersonalized video segments 111 and thedata 112 remain stored at the memory 103 such that further personalizedvideos may be rendered for other communication devices 107-N.

FIG. 13 further depicts another example embodiment of a communicationdevice 107 requesting a personalized video.

For example, also depicted in FIG. 13, the computing device 101 iscausing a personalized icon 1313 to be generated using the personal data116-N, as described with reference to FIG. 7, by providing to the videoprocessing device 105-1, the name 117-N (e.g. “Sally”), the icon data113, and optionally (as depicted) one or more of the sets of data 112for example such that a nonpersonalized layer may be used to generatethe personalized icon 1313. As depicted, however, the video processingdevice 105-1 generates the personalized icon 1313 comprising a “Play”symbol (e.g. from the icon data 113) with the name 117-N “Sally”incorporated therein.

The personalized icon 1313 is provided to the computing device 101 whichmay associate a link 1315 and/or another identifier (such as a UUID andthe like) with the personalized icon 1313, the link 1315, and the like,for requesting a personalized video using the personal data 116-N, thenonpersonalized video segments 111 and the data 112. The link 1315, andthe like, may include the name 117-N, the email address 118-N, and/or anidentifier of the personal data 116-N (such as a UUID and the like),such that when the link 1315 is used to request a personalized video,the computing device 101 may receive the name 117-N, the email address118-N, and/or the identifier reference of the personal data 116-N torender a personalized video. Indeed, the personalized icon 1313 may beassociated with one or more first UUIDs identifying the personalizeddata 116-N, and one or more second UUIDs identifying the segments 111and the data 112.

The computing device 101 may incorporate the personalized icon 1313 andthe associated link 1315, and like, as a virtual button 1317, and thelike into a message 1323, such as an email, and the like, and transmitsthe message 1323 to the communication device 107-N using, for example,the email address 118-N stored in the personal data 116-N that includesthe name 117-N used to generate the personalized icon 1313. As depicted,the message 1323 includes optional text “Press Icon For PersonalizedVideo”, to prompt a user of the communication device 107-N to actuatethe virtual button 1317.

As depicted, the communication device 107-N receives the message 1323and renders the message 1323 at a display device thereof, for example ina messaging application, including the virtual button 1317. It isunderstood by a person of skill in the art that when the virtual button1317 is actuated (e.g. using an input device of the communication device107-N), the communication device 107-N transmits a request 1131, thatincludes the link 1315, to the computing device 101. Receipt of therequest 1131 at the computing device 101 causes the computing device 101to initiate the method 300, as described above with respect to FIG. 8,FIG. 9, FIG. 10, FIG. 11 and FIG. 12, but with the personalized videorendered using the name 117-N “Sally” rather than the name 817 “Bob”. Aperson of skill in the art further understands that the communicationdevice 107-N launches a video streamlining application when the request1131 is transmitted and/or when a manifest is received and/or when afirst video segment identified in the manifest is received.

Furthermore, the name 117-N “Sally” used to render the personalizedvideo may be retrieved from the memory 103 and/or may be received withthe request 1131. Indeed, in embodiments described herein, personal dataassociated with a request, to be used to render a personalized video,may be received with the request and/or the personal data associatedwith a request may be retrieved from a database (e.g. the memory 103)using information received with the request (such as a reference to adatabase record, such as the personal data 116-N, an email address, andthe like).

In this manner, a personalized video may be rendered for each of thecommunication devices 107 and/or users thereof “on demand”, withoutprerendering and storing a personalized video for each, thereby usingprocessing resources to render such personalized videos “on demand”.Furthermore, memory resources in the system 100 are used to store theprerendered nonpersonalized video segments 111 and the data 112, and notpersonalized videos for each of the communication devices 107 and/orusers rendered thereof in advance of the personalized videos beingrequested.

In addition, embodiments described herein depict personalized videosbeing requested in association with webforms and/or in response toreceiving a message that includes a virtual button, and the like, forrequesting a personalized video, such messages generated, for example,from a database of clients and the like. Hence, campaigns to reachexisting clients using personalized videos may be initiated bytransmitting messages to each of the clients, and a personalized videois rendered only for those clients who respond to the message, therebysaving processing resources and/or memory resources as compared toprerendering and storing personalized videos for all the clients storedin the database.

In this specification, elements may be described as “configured to”perform one or more functions or “configured for” such functions. Ingeneral, an element that is configured to perform or configured forperforming a function is enabled to perform the function, or is suitablefor performing the function, or is adapted to perform the function, oris operable to perform the function, or is otherwise capable ofperforming the function.

It is understood that for the purpose of this specification, language of“at least one of X, Y, and Z” and “one or more of X, Y and Z” can beconstrued as X only, Y only, Z only, or any combination of two or moreitems X, Y, and Z (e.g., XYZ, XY, YZ, XZ, and the like). Similar logiccan be applied for two or more items in any occurrence of “at least one. . . ” and “one or more . . . ” language.

The terms “about”, “substantially”, “essentially”, “approximately”, andthe like, are defined as being “close to”, for example as understood bypersons of skill in the art. In some implementations, the terms areunderstood to be “within 10%,” in other implementations, “within 5%”, inyet further implementations, “within 1%”, and in yet furtherimplementations “within 0.5%”.

Those skilled in the art will appreciate that in some implementations,the functionality of devices and/or methods and/or processes describedherein can be implemented using pre-programmed hardware or firmwareelements (e.g., application specific integrated circuits (ASICs),electrically erasable programmable read-only memories (EEPROMs), etc.),or other related components. In other implementations, the functionalityof the devices and/or methods and/or processes described herein can beachieved using a computing apparatus that has access to a code memory(not shown) which stores computer-readable program code for operation ofthe computing apparatus. The computer-readable program code could bestored on a computer readable storage medium which is fixed, tangibleand readable directly by these components, (e.g., removable diskette,CD-ROM, ROM, fixed disk, USB drive). Furthermore, it is appreciated thatthe computer-readable program can be stored as a computer programproduct comprising a computer usable medium. Further, a persistentstorage device can comprise the computer readable program code. It isyet further appreciated that the computer-readable program code and/orcomputer usable medium can comprise a non-transitory computer-readableprogram code and/or non-transitory computer usable medium.Alternatively, the computer-readable program code could be storedremotely but transmittable to these components via a modem or otherinterface device connected to a network (including, without limitation,the Internet) over a transmission medium. The transmission medium can beeither a non-mobile medium (e.g., optical and/or digital and/or analogcommunications lines) or a mobile medium (e.g., microwave, infrared,free-space optical or other transmission schemes) or a combinationthereof.

Persons skilled in the art will appreciate that there are yet morealternative implementations and modifications possible, and that theabove examples are only illustrations of one or more implementations.The scope, therefore, is only to be limited by the claims appendedhereto.

What is claimed is:
 1. A device comprising: a communication interface;and a controller having access to a memory storing: nonpersonalizedvideo segments; and data for rendering personalized video segmentsincluding video fields for population by personal data indicative of oneor more of text and graphics for incorporation into the personalizedvideo segments; the nonpersonalized video segments and the personalizedvideo segments associated with a given order, the controller configuredto: render, according to the given order, the personalized videosegments using the data, with the video fields populated with thepersonal data associated with a request from a communication device suchthat a rendered personalized video segment comprises at least one videoframe that includes the personal data at a location of a respectivevideo field; as rendering of the personalized video segments iscompleted, update, at the communication device, using the communicationinterface, a manifest identifying the nonpersonalized video segments andthe personalized video segments, as rendered, according to the givenorder; and provide to the communication device, using the communicationinterface, video segments identified in the manifest.
 2. The device ofclaim 1, wherein the device is further configured to render thepersonalized video segments by: retrieving, from the data for renderingthe personalized video segments, one or more of a respective prerenderedstatic layer and a respective prerendered non-static layer; rendering arespective personalized layer using the personal data; and combining therespective personalized layer with one or more of the respectiveprerendered static layer and the respective prerendered non-staticlayer.
 3. A system comprising: one or more memories storing:nonpersonalized video segments; and data for rendering personalizedvideo segments including video fields for population by personal dataindicative of one or more of text and graphics for incorporation intothe personalized video segments; the nonpersonalized video segments andthe personalized video segments associated with a given order; acomputing device configured to determine the personal data based on arequest received from a communication device; and one or more videoprocessing devices configured to: render, according to the given order,the personalized video segments using the data, with the video fieldspopulated with the personal data associated with a request from acommunication device, the computing device further configured to: asrendering of the personalized video segments is completed, update, atthe communication device, a manifest identifying the nonpersonalizedvideo segments and the personalized video segments, as rendered,according to the given order; and provide, to the communication device,video segments identified in the manifest.
 4. The system of claim 3,wherein the one or more video processing devices are further configuredto render the personalized video segments by: retrieving, from the datafor rendering the personalized video segments, one or more of arespective prerendered static layer and a respective prerenderednon-static layer; rendering a respective personalized layer using thepersonal data; and combining the respective personalized layer with oneor more of the respective prerendered static layer and the respectiveprerendered non-static layer.
 5. The system of claim 4, wherein the oneor more video processing devices are further configured to render thepersonalized video segments by: retrieving, from the data for renderingpersonalized video segments, transformation data; and rendering therespective personalized layer using the personal data, and according tothe transformation data, such that the respective personalized layer istransformed according to one or more of a previous respectivepersonalized layer and a next respective personalized layer.
 6. Thesystem of claim 3, wherein a first video segment, according to the givenorder, is a first nonpersonalized video segment, and computing device isfurther configured to: in response to receiving the request, update themanifest identifying the first nonpersonalized video segment.
 7. Thesystem of claim 3, wherein the one or more video processing devices arefurther configured to: render the at least a subset of the personalizedvideo segments in parallel.
 8. The system of claim 3, wherein the one ormore video processing devices and the computing device are furtherconfigured to: continue to render the personalized video segments thatoccur later in the personalized video, according to the given order,while providing, to the communication device, the personalized videosegments that occur earlier in the personalized video, as renderingthereof is completed.
 9. The system of claim 3, wherein the computingdevice is further configured to: as rendering of a next personalizedvideo segment is completed, update the manifest to identify the nextpersonalized video segment and any nonpersonalized video segments thatoccur between the next personalized video segment and anotherpersonalized video segment that is still being rendered.
 10. The systemof claim 3, wherein the personal data associated with the request isreceived with the request.
 11. The system of claim 3, wherein thepersonal data associated with the request is retrieved from a databaseusing information received with the request.
 12. A method comprising:accessing, at one or more devices, a memory storing: nonpersonalizedvideo segments; and data for rendering personalized video segmentsincluding video fields for population by personal data indicative of oneor more of text and graphics for incorporation into the personalizedvideo segments; the nonpersonalized video segments and the personalizedvideo segments associated with a given order; rendering, at the one ormore devices, according to the given order, the personalized videosegments using the data, with the video fields populated with thepersonal data associated with a request from a communication device suchthat a rendered personalized video segment comprises at least one videoframe that includes the personal data at a location of a respectivevideo field; as rendering of the personalized video segments iscompleted, updating, via the one or more devices, at the communicationdevice, a manifest identifying the nonpersonalized video segments andthe personalized video segments, as rendered, according to the givenorder; and providing, via the one or more devices, to the communicationdevice, video segments identified in the manifest.
 13. The method ofclaim 12, further comprising rendering the personalized video segmentsby: retrieving, from the data for rendering personalized video segments,one or more of a respective prerendered static layer and a respectiveprerendered non-static layer; rendering a respective personalized layerusing the personal data; and combining the respective personalized layerwith one or more of the respective prerendered static layer and therespective prerendered non-static layer.
 14. The method of claim 13,further comprising rendering the personalized video segments by:retrieving, from the data for rendering personalized video segments,transformation data; and rendering the respective personalized layerusing the personal data, and according to the transformation data, suchthat the respective personalized layer is transformed according to oneor more of a previous respective personalized layer and a nextrespective personalized layer.
 15. The method of claim 12, wherein afirst available video segment, according to the given order, is a firstnonpersonalized video segment, and the method further comprises: inresponse to receiving the request, transmitting the manifest identifyingthe first nonpersonalized video segment.
 16. The method of claim 12,further comprising: rendering of the at least a subset of thepersonalized video segments in parallel.
 17. The method of claim 12,further comprising: continuing to render the personalized video segmentsthat occur later in the personalized video, according to the givenorder, while providing, to the communication device, the personalizedvideo segments that occur earlier in the personalized video, as they arecompleted.
 18. The method of claim 12, further comprising: as renderingof a next personalized video segment is completed, updating the manifestto identify the next personalized video segment and any nonpersonalizedvideo segments that occur between the next personalized video segmentand another personalized video segment that is still being rendered. 19.The method of claim 12, wherein the personal data associated with therequest is received with the request.
 20. The method of claim 12,wherein the personal data associated with the request is retrieved froma database using information received with the request.